home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
FishMarket 1.0
/
FishMarket v1.0.iso
/
fishies
/
101-125
/
disk_107
/
svtools
/
fragit
/
readme
< prev
Wrap
Text File
|
1992-05-06
|
2KB
|
52 lines
Fragit
or how to fragment CHIP ram, or possible explaination for
mysterious out of memory errors.
Introduction:
A few days ago I found one of my programs was fragmenting CHIP
memory, while apparantly not loosing any memory. After having
read many USENET messages claiming that this would be very
difficult if not impossible to do (or else very unusual) I was
very mystified. So I decided to investigate...
How to do it:
Do this from the CLI, but it should happen from the Workbench too.
1 - Make two CLI windows, make one the full size of the display
and the other at least half the height of the display.
2 - Run either Avail or my memlist program to see what the size
of the largest CHIP memory blocks are.
3 - Now run fragit, the following will happen:
- a small, empty, window will appear in the middle of the
display, for memory to fragment this window MUST overlap
the other two windows in such a way that at some point
they stack THREE deep.
- a CUSTOMSCREEN, hires, interlaced, 16 colours (lots of memory)
will open up.
- the small window on the workbench will now be deleted.
- the CUSTOMSCREEN will now close down.
- memory should now be fragmented.
4 - Now run the memlist program to see what happened, DO NOT move
or resize any windows before doing this. You should see that
the biggest block of CHIP ram got split into two smaller
blocks. This is a problem because if the user ran another
memory intensive program right away he could get OUT OF MEMORY
type errors.
5 - Now either move or resize the smaller window slightly and rerun
the memlist program, you should see the two largest CHIP ram
blocks change sizes. You will now have virtually the same
memory distribution as you had before doing all this. Also
note that at no time was memory lost.
What to do?
Good question...